Data Flows from Source Systems into Corvus

Any Source System at your site can connect to Corvus Axiom. It is important to understand that data flows in one direction, from the Source System and into Corvus. Please see the below diagram, explaining the Corvus Data Flow:

Corvus Data Flow Example – Truck Cycles

Data flows from Source Systems and is mapped to cycles and shift actuals in Corvus.

Manual Amendments to Process Activity Shift Actuals

If manual amendments are made to the Process Activities Shift Actuals, please remember these edits will not be saved to the source system, as data only flows in one direction:

Shift Locking and Data Flow Effects

Once a shift has been locked in Corvus, any changes made to the Source System data will not flow through to Corvus. If you wish to re-process the data through to Corvus once the Source System data has been modified, you will be required to unlock the appropriate Corvus shift, re-process the data via External Source Systems External Source Systems Module module, verify the data import has been successful and relock the shift, via the Shift Status Shift Status module, to prevent any further updates effecting the shift.